-
Notifications
You must be signed in to change notification settings - Fork 25
refactor!: move container options to shared containers key
#387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor!: move container options to shared containers key
#387
Conversation
agitter
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The contributing guide will also need updates.
Documentation build overview
Show files changed (6 files in total): 📝 6 modified | ➕ 0 added | ➖ 0 deleted
|
|
3cadfc4 was the only change necessary in |
|
This has been tagged with |
agitter
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like previous review comments were addressed.
The hash_level usage is still unintuitive to me, but I trust it will make more sense once I see the future changes.
Closes #297. [See #297 for extra motivation of the
containerskey beyond the diamond dependency reason below]This is 1/2 PRs being extracted from #329 to make it easier to add testing to
dsub. The second PR is #390. (See the note after the horizontal break)[See the diff without whitespace changes from config indentation]
I've avoided splitting this PR up before since the extra file is motivated by #329: specifically, we move
ContainerSettingstocontainer_schema.pyinstead of keeping it inschema.pyto prevent the future dependency diamond of:containers.pydepends on the schema for getting extra container settings (the follow-up PR above is going to refinecontainers.py's dependency on the schema by specifically only making it depend oncontainer_schema.py)[algorithm].py, because ofrun_containers, depends oncontainers.pyschema.pywill, thanks to feat!: typed PRA#run #329, depend on[algorithm].pyfor all algorithms.I want to be able to pass a more rich suite of options to
run_container_dsub(specifically,local, to specify thatdsubshould be mocked withdockeras specified indsub's documentation), which causes a strangedsub_localparameter to be propagated up all the way torun_container. Instead of adding this parameter or making an auxiliary object to pass both parameters in, it seemed better to reuse the object we were reading out of the global config anyway (we do this all overcontainers.pyanyway for container parameters, so it might be better overall to pass them in as a parameter).